Skip to content

feat: add /orchestrate — structured workflow orchestration#53

Closed
robotmem wants to merge 1 commit intogarrytan:mainfrom
robotmem:feat/orchestrate-skill
Closed

feat: add /orchestrate — structured workflow orchestration#53
robotmem wants to merge 1 commit intogarrytan:mainfrom
robotmem:feat/orchestrate-skill

Conversation

@robotmem
Copy link

Summary

  • Adds a new /orchestrate skill that chains existing gstack skills into a structured pipeline
  • One command runs the full lifecycle: triage → plan → plan review → execute → code review → QA → ship → retro
  • Zero changes to existing skills — one new directory (orchestrate/), one file (SKILL.md)

What it does

/orchestrate "add user authentication" runs an 8-phase pipeline:

Phase What happens gstack skill called
1. Triage Classify task type + scope assessment
2. Plan Product + engineering planning /plan-ceo-review/plan-eng-review
3. Plan Review Roundtable gate (3 expert perspectives)
4. Execute Write code within approved scope
5. Code Review Paranoid review with classification /review
6. QA Diff-aware testing /qa
7. Ship Automated release /ship
8. Retro Optional retrospective /retro

Key design decisions

  • Reuses existing scope modes — Triage maps directly to /plan-ceo-review's SCOPE EXPANSION / HOLD SCOPE / SCOPE REDUCTION
  • Phase gates with rejection loops — Plan review and code review are quality gates with max 3 rounds before escalating to user
  • Roundtable plan review — Phase 3 adopts 3 named software engineering experts (Linus Torvalds, Bryan Cantrill, Martin Fowler) to stress-test the plan from different angles
  • Review classification — Reuses /review's VALID / ALREADY FIXED / FALSE POSITIVE classification. Only VALID issues trigger rejection
  • QA mode selection — Automatically selects full/diff-aware/quick mode based on scope from triage
  • 292 lines — Single SKILL.md file, pure prompt, no TypeScript/Bun dependency

Test plan

  • YAML frontmatter matches gstack format (name, version, description, allowed-tools)
  • Update Check section matches other skills
  • All referenced skills exist (plan-ceo-review, plan-eng-review, review, qa, ship, retro)
  • Manual test: /orchestrate "add a feature" runs the full pipeline
  • Manual test: /orchestrate --from plan "task" resumes from Phase 2
  • Manual test: /orchestrate --skip-retro "task" skips Phase 8

🤖 Generated with Claude Code

One command runs the full lifecycle: triage → plan → plan review →
execute → code review → QA → ship → retro.

Chains existing gstack skills (/plan-ceo-review, /plan-eng-review,
/review, /qa, /ship, /retro) into a disciplined pipeline with
phase gates and rejection loops.

Key features:
- Phase 1 Triage: classify task type + scope assessment
  (reuses /plan-ceo-review's EXPAND/HOLD/REDUCE modes)
- Phase 2 Plan: /plan-ceo-review → /plan-eng-review → user confirms
- Phase 3 Plan Review: roundtable gate with 3 named engineering
  experts (Linus Torvalds, Bryan Cantrill, Martin Fowler)
- Phase 4 Execute: write code within approved scope
- Phase 5 Code Review: /review with VALID/FIXED/FP classification
- Phase 6 QA: /qa with mode selection based on scope
- Phase 7 Ship: /ship automated release
- Phase 8 Retro: /retro (optional)

Zero changes to existing skills. One new directory, one file.
@robotmem robotmem closed this by deleting the head repository Mar 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant